﻿
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- saved from url=(0014)about:internet -->
<html xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:mssdk="winsdk" xmlns:script="urn:script" xmlns:build="urn:build" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="Description" content="The .shell command launches a shell process and redirects its output to the debugger, or to a specified file."/>
<meta name="MSHAttr" content="PreferredSiteName:MSDN"/>
<meta name="MSHAttr" content="PreferredLib:/library/windows/hardware"/>
<title>.shell (Command Shell)</title>

<meta name="MS-HAID" content="r22_metacmds_S_6a45ee2d-cc3f-4f6b-a649-87dde063d5ca.xml"/>


<link rel="STYLESHEET" type="text/css" HREF="../common/backsdk4.css"/>





<style>
html,div { margin: 0; padding: 0;}

body {
	padding: 0px;
	margin: 0px;
	overflow: auto;
	height: 100%;
}

#winchm_template_button{
	float: right;
	width: 93px;
	top: 7px;
	position: relative;
	text-align: right;
	right: 5px;
	height: auto;
}

#winchm_template_top{
	padding: 0px;
	margin: 0px;
	border-bottom: 1px solid #9B9B9B;
	background-color: #B1CEFE;
}

#winchm_template_navigation{
	margin: 0px;
	padding-top: 7px;
	padding-left: 7px;
	padding-bottom: 3px;
	padding-right: 0px;
	font-size: 8.5pt;
	font-family: Arial, Helvetica, sans-serif;
	font-weight: normal;
	color: #585858;
}

#winchm_template_title{
	margin: 0px;
	padding-top: 4px;
	padding-left: 7px;
	padding-bottom: 7px;
	padding-right: 0px;
	font-size: 18px; 
	font-family: Verdana, Geneva, sans-serif;
	color: #363636;
}

#winchm_template_content{
	margin-top: 20px;
	margin-left: 15px;
	margin-bottom: 20px;
	margin-right: 15px;
	width: auto  !important;
	width: 100%;
}

#winchm_template_footer{
	border-width: 1px;
	border-color: #B1CEFE;
	border-top-style: solid;
	margin-top: 15px;
	margin-left: 15px;
	margin-bottom: 20px;
	margin-right: 15px;
	padding-top: 7px;
	padding-left: 0px;
	padding-bottom: 0px;
	padding-right: 0px;
	font-family: arial, helvetica, sans-serif;
	font-size: 8.5pt;
	color: #696969;
	width: auto;
	text-align: left;
}


#winchm_template_container{
	margin: 0px;
	padding: 0px;
	position: static;
	padding-bottom: 3px;
	overflow: auto;
	background-color: #FFFFFF;
}


@media print
{
#winchm_template_container{
	position: static;	
	margin: 0px;
	padding: 5px;
	
	width: auto;
	height: auto;
	overflow: auto;
}
#winchm_template_button{
visibility:hidden;
}
}

#winchm_template_navigation A:link	{text-decoration: none; color:#004080}
#winchm_template_navigation A:visited  {text-decoration: none; color: #004080}
#winchm_template_navigation A:active {text-decoration: none; color: #004080 }
#winchm_template_navigation A:hover {text-decoration: none;color: #0080FF}

A:link	{text-decoration: underline; color:#0033CC}
A:visited  {text-decoration: underline; color: #0033CC}
A:active {text-decoration: underline; color: #0033CC }
A:hover {text-decoration: underline;color: #FF0000;}
</style>
<script type="text/javascript">
function isMobile(){
Agent = window.navigator.userAgent;
if (Agent.indexOf("iPhone")>=1 || Agent.indexOf("iPad")>=1 || Agent.indexOf("iPod")>=1 || Agent.indexOf("Android")>=1){
return true;
}else{
return false;	
}

}
function d_onresize(){
if (window.navigator.userAgent.indexOf("MSIE")>=1){
document.getElementById('winchm_template_container').style.pixelWidth = document.body.offsetWidth - 3;
document.getElementById('winchm_template_container').style.pixelHeight = document.body.offsetHeight - document.getElementById('winchm_template_top').offsetHeight - 4;
}
document.getElementById('winchm_template_container').style.top = document.getElementById('winchm_template_top').offsetHeight + 'px';
}

function d_onbeforeprint(){
document.getElementById('winchm_template_container').style.width = 'auto';
document.getElementById('winchm_template_container').style.height = 'auto';
}

function d_onafterprint(){
d_onresize();
}

if(!isMobile()){

window.onload = d_onresize;
window.onresize = d_onresize;
window.onbeforeprint = d_onbeforeprint;
window.onafterprint = d_onafterprint;

document.write("<style>\n");
document.write("body {overflow: hidden;}\n");
document.write("#winchm_template_container {position: absolute;overflow: auto;top : 0px;right: 0px;bottom: 0px;left: 0px;}\n");
document.write("</style>\n");
}

</script>
</head>
<body><script language="JavaScript" type="text/JavaScript">
function syn(){
if(parent.nav.tree){
 if(parent.nav.tree.loaded){
  parent.nav.tree.selectNode(2180);
 }else{
  setTimeout("syn()",500);
}
  }else{
  setTimeout("syn()",500);
  }}
if(parent!=self){
  setTimeout("syn()",100);
}else{
  parent.location.href = "../../index.htm?page=debugger/_shell__command_shell_.htm";
}
originalOnload = window.onload;
if(originalOnload==null){
window.onload = function(){parent.contentLoaded = true;};
}else{
window.onload = function(){originalOnload();parent.contentLoaded = true;};
}
</script> 


<div id="winchm_template_top">
	<div id="winchm_template_button"><A href="_setdll__set_default_extension_dll_.htm" title="Previous topic"><img id="winchm_template_prev" alt="Previous topic" src="../template2/btn_prev_n.gif" border="0"></a><A href="_settings__set_debug_settings_.htm" title="Next topic"><img id="winchm_template_next" alt="Next topic" src="../template2/btn_next_n.gif" border="0"></a></div>
	<div id="winchm_template_navigation">Help &gt; 
<A href="introduction6.htm">Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)</A> &gt; <A href="debugger_reference.htm">Debugger Reference</A> &gt; <A href="debugger_commands.htm">Debugger Commands</A> &gt; <A href="meta_commands.htm">Meta-Commands</A> &gt; </div>
	<div id="winchm_template_title">.shell (Command Shell)</div>
</div>
<div id="winchm_template_container">
	<div id="winchm_template_content"><div id="mainSection"><p>The <b>.shell</b> command launches a shell process and redirects its output to the debugger, or to a specified file.</p>
<p></p>
<p></p>
<pre class="syntax"><b>.shell [</b><i>Options</i><b>] [</b><i>ShellCommand</i><b>]</b> 
<b>.shell -i </b><i>InFile</i><b> [-o </b><i>OutFile</i><b> [-e </b><i>ErrFile</i><b>]] [</b><i>Options</i><b>] </b><i>ShellCommand</i></pre>
<h2><a id="ddk_meta_command_shell_dbg"></a><a id="DDK_META_COMMAND_SHELL_DBG"></a>Parameters</h2>
<p></p>
<dl>
<dt><a id="_______InFile______"></a><a id="_______infile______"></a><a id="_______INFILE______"></a>       <i>InFile</i>      </dt>
<dd>
<p>Specifies the path and file name of a file to be used for input. If you intend to offer no input after the initial command, you can specify a single hyphen (-) instead of <i>InFile</i>, with no space before the hyphen.</p>
</dd>
<dt><a id="_______OutFile______"></a><a id="_______outfile______"></a><a id="_______OUTFILE______"></a>       <i>OutFile</i>      </dt>
<dd>
<p>Specifies the path and file name of a file to be used for standard output. If <b>-o</b><b> </b><i>OutFile</i> is omitted, output is sent to the Debugger Command window. If you do not want this output displayed or saved in a file, you can specify a single hyphen (-) instead of <i>OutFile</i>, with no space before the hyphen.</p>
</dd>
<dt><a id="_______ErrFile______"></a><a id="_______errfile______"></a><a id="_______ERRFILE______"></a>       <i>ErrFile</i>      </dt>
<dd>
<p>Specifies the path and file name of a file to be used for error output. If -e ErrFile is omitted, error output is sent to the same place as standard output. If you do not want this output displayed or saved in a file, you can specify a single hyphen (-) instead of <i>ErrFile</i>, with no space before the hyphen.</p>
</dd>
<dt><a id="_______Options______"></a><a id="_______options______"></a><a id="_______OPTIONS______"></a>       <i>Options</i>      </dt>
<dd>
<p>Can be any number of the following options:</p>
<p></p>
<dl>
<dt><a id="-ci__Commands_"></a><a id="-ci__commands_"></a><a id="-CI__COMMANDS_"></a><b>-ci "</b><i>Commands</i><b>"</b></dt>
<dd>
<p>Processes the specified debugger commands, and then passes their output as an input file to the process being launched. <i>Commands</i> can be any number of debugger commands, separated by semicolons, and enclosed in quotation marks.</p>
</dd>
<dt><a id="-x"></a><a id="-X"></a><b>-x</b></dt>
<dd>
<p>Causes any process being spawned to be completely detached from the debugger. This allows you to create processes which will continue running even after the debugging session ends.</p>
</dd>
</dl>
</dd>
<dt><a id="_______ShellCommand______"></a><a id="_______shellcommand______"></a><a id="_______SHELLCOMMAND______"></a>       <i>ShellCommand</i>      </dt>
<dd>
<p>Specifies the application command line or Microsoft MS-DOS command to be executed.</p>
</dd>
</dl>
<h3><a id="Environment"></a><a id="environment"></a><a id="ENVIRONMENT"></a>Environment</h3>
<table>
<tr>
<td>
<p><b>Modes</b></p>
</td>
<td>
<p>user mode, kernel mode</p>
</td>
</tr>
<tr>
<td>
<p><b>
          Targets</b></p>
</td>
<td>
<p>live, crash dump</p>
</td>
</tr>
<tr>
<td>
<p><b>Platforms</b></p>
</td>
<td>
<p>all </p>
</td>
</tr>
</table>
<p> </p>
<h3><a id="Additional_Information"></a><a id="additional_information"></a><a id="ADDITIONAL_INFORMATION"></a>Additional Information</h3>
<p>For other ways of accessing the command shell, see <a href="#Bookmark1267">Using Shell Commands</a>.</p>
<h2>Remarks</h2>
<p>The <b>.shell</b> command is not supported when the output of a user-mode debugger is redirected to the kernel debugger. For more information about redirecting output to the kernel debugger (sometimes called NTSD over KD), see <a href="#Bookmark1312">Controlling the User-Mode Debugger from the Kernel Debugger</a>.</p>
<p>The entire line after the <b>.shell</b> command will be interpreted as a Windows command (even if it contains a semicolon). This line should not be enclosed in quotation marks. There must be a space between <b>.shell</b> and the <i>ShellCommand</i> (additional leading spaces are ignored).</p>
<p>The output from the command will appear in the Debugger Command window, unless the <b>-o</b><b> </b><i>OutFile</i> parameter is used.</p>
<p>Issuing a <b>.shell</b> command with no parameters will activate the shell and leave it open. All subsequent commands will be interpreted as Windows commands. During this time, the debugger will display messages reading <b>&lt;.shell process may need input&gt;</b>, and the WinDbg prompt will be replaced with an <b>Input&gt;</b> prompt. Sometimes,  a separate Command Prompt window will appear when the debugger leaves the shell open. This window should be ignored; all input and output will be done through the Debugger Command window.</p>
<p>To close this shell and return to the debugger itself, type <b>exit</b> or <b>.shell_quit</b>. (The <b>.shell_quit</b> command is more powerful, because it works even if the shell is frozen.)  </p>
<p>This command cannot be used while debugging CSRSS, because new processes cannot be created without CSRSS being active.</p>
<p>You can use the -ci flag to run one or more debugger commands and then pass their output to a shell process. For example, you could pass the output from the <a href="#Bookmark2417"><b>!process 0 7</b></a> command to a Perl script by using the following command:</p>
<pre class="syntax" xml:space="preserve"><code>0:000&gt; .shell -ci "!process 0 7" perl.exe parsemyoutput.pl </code></pre></div></div>	
	<div id="winchm_template_footer">Copyright &copy; 2019. All rights 
reserved. (To change the copyright info, just edit it in template.)</div>
</div>

</body>
</html>
